The ID or slug of the organization the resource belongs to.

The new slug for the organization, which needs to be unique.

The new name for the organization.

Specify `true` to opt-in to new features before they're released to the public.

Specify `true` to hide AI features from the organization.

Specify `true` to enable Code Coverage Insights. This feature is only available for organizations on the Team plan and above. Learn more about Codecov [here](/product/codecov/).

The default role new members will receive. * `member` - Member * `admin` - Admin * `manager` - Manager * `owner` - Owner

Specify `true` to allow organization members to freely join any team.

Specify `true` to allow members to delete events (including the delete & discard action) by granting them the `event:admin` scope.

Specify `true` to allow members to create, edit, and delete alert rules by granting them the `alerts:write` scope.

The role required to download event attachments, such as native crash reports or log files. * `member` - Member * `admin` - Admin * `manager` - Manager * `owner` - Owner

The role required to download debug information files, ProGuard mappings and source maps. * `member` - Member * `admin` - Admin * `manager` - Manager * `owner` - Owner

Specify `true` to enable granular replay permissions, allowing per-member access control for replay data.

A list of user IDs who have permission to access replay data. Requires the hasGranularReplayPermissions flag to be true to be enforced.

The type of display picture for the organization. * `letter_avatar` - Use initials * `upload` - Upload an image

The image to upload as the organization avatar, in base64. Required if `avatarType` is `upload`.

Specify `true` to require and enforce two-factor authentication for all members.

Specify `true` to allow sharing of limited details on issues to anonymous users.

Specify `true` to enable enhanced privacy controls to limit personally identifiable information (PII) as well as source code in things like notifications.

Specify `true` to allow Sentry to scrape missing JavaScript source context when possible.

How many native crash reports (such as Minidumps for improved processing and download in issue details) to store per issue. * `0` - Disabled * `1` - 1 per issue * `5` - 5 per issue * `10` - 10 per issue * `20` - 20 per issue * `50` - 50 per issue * `100` - 100 per issue * `-1` - Unlimited

Specify `true` to allow users to request to join your organization.

Specify `true` to require server-side data scrubbing for all projects.

Specify `true` to apply the default scrubbers to prevent things like passwords and credit cards from being stored for all projects.

A list of additional global field names to match against when scrubbing data for all projects.

A list of global field names which data scrubbers should ignore.

Specify `true` to prevent IP addresses from being stored for new events on all projects.

Advanced data scrubbing rules that can be configured for each project as a JSON string. The new rules will only apply to new incoming events. For more details on advanced data scrubbing, see our [full documentation](/security-legal-pii/scrubbing/advanced-datascrubbing/). > Warning: Calling this endpoint with this field fully overwrites the advanced data scrubbing rules. Below is an example of a payload for a set of advanced data scrubbing rules for masking credit card numbers from the log message (equivalent to `[Mask] [Credit card numbers] from [$message]` in the Sentry app) and removing a specific key called `foo` (equivalent to `[Remove] [Anything] from [extra.foo]` in the Sentry app): ```json { relayPiiConfig: "{\"rules":{\"0\":{\"type\":\"creditcard\",\"redaction\":{\"method\":\"mask\"}},\"1\":{\"type\":\"anything\",\"redaction\":{\"method\":\"remove\"}}},\"applications\":{\"$message\":[\"0\"],\"extra.foo\":[\"1\"]}}" } ```

A list of local Relays (the name, public key, and description as a JSON) registered for the organization. This feature is only available for organizations on the Business and Enterprise plans. Read more about Relay [here](/product/relay/). Below is an example of a list containing a single local Relay registered for the organization: ```json { trustedRelays: [ { name: "my-relay", publicKey: "eiwr9fdruw4erfh892qy4493reyf89ur34wefd90h", description: "Configuration for my-relay." } ] } ```

Specify `true` to allow the Sentry Slack integration to post replies in threads for an Issue Alert notification. Requires a Slack integration.

Specify `true` to allow the Sentry Slack integration to post replies in threads for a Metric Alert notification. Requires a Slack integration.

Specify `true` to restore an organization that is pending deletion.